Deploying edge computing

ABSTRACT

Techniques discussed herein can facilitate edge computing in connection with a variety of deployment scenarios. Various embodiments can facilitate one or more of: deploying UPF(s) (User Plane Function(s)) to support edge computing; removing UPF(s) not needed for edge computing; deploying local DN(s) (Data Network(s)); E2E (Edge-to-Edge) OSS (Operations Support System) deployment scenarios; and providing RAN (Radio Access Network) condition data to support various applications (e.g., autonomous driving).

REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/753,834 filed Oct. 31, 2018, entitled “SYSTEM ANDMETHOD TO DEPLOY EDGE COMPUTING”, the contents of which are hereinincorporated by reference in their entirety.

BACKGROUND

Mobile communication has evolved significantly from early voice systemsto today's highly sophisticated integrated communication platform. Thenext generation wireless communication system, 5G (or new radio (NR))will provide access to information and sharing of data anywhere, anytimeby various users and applications. NR is expected to be a unifiednetwork/system that target to meet vastly different and sometimeconflicting performance dimensions and services. Such diversemulti-dimensional requirements are driven by different services andapplications. In general, NR will evolve based on 3GPP (Third GenerationPartnership Project) LTE (Long Term Evolution)-Advanced with additionalpotential new Radio Access Technologies (RATs) to enrich people liveswith better, simple and seamless wireless connectivity solutions. NRwill enable everything connected by wireless and deliver fast, richcontents and services.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a system that facilitates supportof edge computing according to various deployment scenarios, inaccordance with various embodiments discussed herein.

FIG. 2 is a diagram illustrating 3GPP network elements working withnon-3GPP network elements to provide various services via edgecomputing, in connection with various aspects discussed herein.

FIG. 3 is a diagram illustrating an example scenario of an edgecomputing network deployment, in connection with various aspectsdiscussed herein.

FIG. 4 is a diagram illustrating an example E2E (End-to-End) OSS(Operations Support System) edge computing deployment scenario, inconnection with various aspects discussed herein.

FIG. 5 is a diagram illustrating an example peer-to-peer edge computingdeployment scenario, in connection with various aspects discussedherein.

DETAILED DESCRIPTION

Embodiments described herein can be implemented into a system using anysuitably configured hardware and/or software. In various aspects,embodiments discussed herein can facilitate support of edge computing inconnection with a variety of deployment scenarios.

Referring to FIG. 1 , illustrated is a block diagram of a system 100employable at a component of a 3GPP (Third Generation PartnershipProject) network or non-3GPP management system that facilitates supportof edge computing applications in a variety of scenarios, inembodiments. System 100 can include processor(s) 110 comprisingprocessing circuitry and associated interface(s) (e.g., a communicationinterface for communicating with communication circuitry 120, a memoryinterface for communicating with memory 130, etc.), communicationcircuitry 120 (e.g., comprising circuitry for wired and/or wirelessconnection(s), e.g., transmitter circuitry (e.g., associated with one ormore transmit chains) and/or receiver circuitry (e.g., associated withone or more receive chains), wherein transmitter circuitry and receivercircuitry can employ common and/or distinct circuit elements, or acombination thereof), and a memory 130 (which can comprise any of avariety of storage mediums and can store instructions and/or dataassociated with one or more of processor(s) 110 or transceiver circuitry120). Specific types of embodiments (e.g., UE embodiments) can beindicated via subscripts (e.g., system 100 _(UE) comprising processor(s)110 _(UE), communication circuitry 120 _(UE), and memory 130 _(UE)). InBS embodiments (e.g., system 100 _(gNB)) and network component (e.g.,UPF (User Plane Function), etc.) embodiments (e.g., system 100 _(UPF))processor(s) 110 _(gNB) (etc.), communication circuitry 120 _(gNB)(etc.), and memory 130 _(gNB) (etc.) can be in a single device or can beincluded in different devices, such as part of a distributedarchitecture. In embodiments, signaling or messaging between differentembodiments of system 100 (e.g., 100 ₁ and 100 ₂) can be generated byprocessor(s) 110 ₁, transmitted by communication circuitry 120 ₁ over asuitable interface or reference point (e.g., N4, etc.), received bycommunication circuitry 120 ₂, and processed by processor(s) 110 ₂.

The 5G (Fifth Generation) networks are intended to support various newservices such as IoT (Internet of Things), Cloud-based services,industrial control, autonomous driving, mission critical communications,etc., based on the network slicing technology. Some services, forexample, autonomous driving, have ultra-low latency and high datacapacity targets (or requirements, etc.), due to safety and performanceconcerns. 5GC (5G Core Network) system architecture as defined in 3GPP(Third Generation Partnership Project) TS (Technical Specification)23.501 supports edge computing to enable such services by applicationsthat are hosted closer to the UE's access point of attachment in orderto reduce the end-to-end latency and the load on the transport network.

Referring to FIG. 2 , illustrated is a diagram showing how 3GPP networkelements work with non-3GPP network elements, such as AF (ApplicationFunction) 260 and local DN (Data Network) 280 to provide variousservices (e.g., those discussed above, etc.) such as example application270 via edge computing, in connection with various aspects discussedherein. The AF 260 can send requests to SMF (Session ManagementFunction) 240 via PCF (Policy Function) 250 or NEF (Network ExposureFunction) (not shown) to influence UPF (User Plane Function) 230 _(i)(re)selection and traffic steering to route the UE 210 traffic from theselected UPF 230 _(i) to the application 270 in the local Data Network280 via the N6 reference point.

The end-to-end latency of the traffic traveling from UE 210 to local DN280 includes the latency both inside the 3GPP network (e.g., RAN 220 and5GC) and outside the 3GPP network. The latency within the 3GPP networkis relevant to 5G QoS (Quality of Service), as described in clause5.7.3.1 in TS 23.501, which is the QoS a data flow receives edge-to-edgebetween the UE 210 and the UPF 230 _(i). The latency outside the 3GPPnetwork is determined by the QoS over N6 reference point that is relatedto the geographical locations of UPF 230 _(i) and local DN 280. Thus, itis important to deploy the local DN 280 and UPF 230 _(i) in a mannerthat meets the end-to-end latency target(s) (or requirement(s), etc.) ofthe service(s).

Various embodiments discussed herein can facilitate operator deploymentof UPF(s) and local DN(s) to support edge computing networks, inconnection with various edge computing deployment scenarios. A first setof embodiments relate to E2E (End-to-End) OSS (Operations SupportSystem) deployment scenarios, while a second set of embodiments relateto peer-to-peer edge computing management deployment scenarios. Inconnection with these embodiments and scenarios, use cases andcapabilities (e.g., or requirements, etc.) are discussed herein,comprising: (a) Deploying UPF(s) to support edge computing; (b) RemovingUPF(s) not needed for edge computing; (c) Local DN deployment; (d) E2EOSS deployment scenarios; and (e) RAN condition data.

Edge Computing Deployment Scenarios

Referring to FIG. 3 , illustrated is an example scenario 300 of an edgecomputing network deployment, in connection with various aspectsdiscussed herein. In scenario 300, NR cells 310 _(i) and data centers DC#1-#4 (290 ₁-290 ₄), DC #11-#12 (290 ₁₁-290 ₁₂) have been deployed. Whenan operator decides to deploy an edge computing application for UEsconnected to NR cell #1 310 ₁, it can select DC #2 290 ₂ to deploy UPF#2 230 ₂, and DC #11 290 ₁₁ to deploy local DN #1 280 ₁, based on theQoS targets (or requirements, etc.) between UEs and local DN #1 280 ₁that meet the end-to-end QoS targets (or requirements, etc.) imposed bythe application. The operator can connect UPF #2 230 ₂ to local DN #1280 ₁ via virtual link, as shown in FIG. 3 .

The deployment of network functions in 3GPP networks and non-3GPPnetworks to support edge computing involves communication between 3GPPmanagement system and non-3GPP management systems, such as ETSI(European Telecommunications Standards Institute) NFV (Network FunctionVirtualization) MANO (Management and Orchestration) and ETSI MEC(Multi-Access Edge Computing).

E2E OSS Deployment Scenario

Referring to FIG. 4 , illustrated is a diagram of an example E2E(End-to-End) OSS (Operations Support System) deployment scenario 400, inconnection with various aspects discussed herein. In example deploymentscenario 400, E2E OSS 410 is responsible for coordination among the 3GPPmanagement system 420, non-3GPP management systems 430, which cancomprise edge computing (e.g., ETSI MEC) management system 432responsible for the management of AF (e.g., 260) and local DN (e.g., 280_(i)), and ETSI NFV MANO 434 to support the deployment of edge computingin 3GPP networks.

E2E OSS 410 can comprise information (e.g., e2e QoS requirements of edgecomputing applications, the topology of the UPF 230 _(i) and local DN280 _(i), etc.) that facilitates deployment of the edge computingnetwork. E2E OSS 410 is responsible for dividing the e2e QoSrequirements into 5G QoS for 3GPP networks and QoS over N6 for non-3GPPnetworks, and setting up the connection between UPF 230 _(i) and localDN 280 _(i). In various aspects, E2E OSS 210 can communicate with: (1)3GPP management system 420 to instantiate and configure the 3GPP NFs(e.g. UPF); (2) Non-3GPP edge computing management system 434 toinstantiate and configure the local DN 280 _(i); and (3) Non-3GPP ETSINFVO 432 to establish and manage the connection between the UPF 230 _(i)and local DN 280 _(i), with the corresponding QoS targets (orrequirements, etc.).

Peer-to-Peer Edge Computing Management Deployment Scenario

Referring to FIG. 5 , illustrated is an example peer-to-peer edgecomputing management deployment scenario 500, in connection with variousaspects discussed herein. In example scenario 500, the deployment ofedge computing in 3GPP networks involves communication among 3GPPmanagement system 420 (e.g., within OSS 510), non-3GPP management system430, which can comprise edge computing management system 434 and ETSINFV MANO 432.

In some aspects, 3GPP management system 420 can initiate the edgecomputing deployment by requesting the edge computing management system434 to deploy the local DN 280 _(i), and NFVO (NFV Orchestrator) of NFVMANO 432 to connect the UPF 230 _(i) and local DN 280 _(i) with the QoSover N6 requirements for the connection (e.g. virtual link) between UPF230 _(i) and local DN 280 _(i).

In other aspects, edge computing management system 434 can initiate theedge computing deployment by requesting the 3GPP management system 420to deploy the UPF 230 _(i), and NFVO of NFV MANO 432 to connect the UPF230 _(i) and local DN 280 _(i) with the QoS target(s) (orrequirement(s), etc.) for the connection between UPF 230 _(i) and localDN 280 _(i).

Example Use Cases Deploy UPF to Support Edge Computing

Introduction: An operator decides to deploy UPF(s) (e.g., 230 _(i)) tosupport edge computing application(s) for UE(s) in a specific area. TheUPF(s) can be deployed in locations where the data transported betweenUE and UPF can meet the 5G QoS targets (or requirements, etc.).

Pre-conditions: the 3GPP management system (e.g., 420) has received the5G QoS targets (or requirements, etc.) of the edge computing application(e.g., 270).

Description: (1) 3GPP management system requests NFVO (e.g., of NFV MANO432) to instantiate the UPF (e.g., 230 _(i)) at a location that isdetermined by the 5G QoS targets (e.g., or requirements); (2) NFVOresponds that the UPF has been instantiated successfully; and (3) 3GPPmanagement system configures SMF (e.g., 240) to add the newlyinstantiated UPF to the UPF list with the UPF location to assist UPFselection for traffic steering.

Post-conditions: The UPF is available to support the edge computingapplication.

Remove UPF not Needed for Edge Computing

Introduction: An operator decides to remove a UPF (e.g., 230 _(i)) thatis no longer needed to support edge computing applications.

Pre-conditions: UPF supporting edge computing application has beeninstantiated.

Description: (1) 3GPP management system (e.g., 420) requests NFVO (e.g.,of NFV MANO 432) to terminate the UPF; (2) NFVO responds that the UPFhas been terminated successfully; and (3) 3GPP management systemconfigures SMF (e.g., 240) to remove the UPF that has been terminatedfrom a UPF list serving the edge computing.

Post-conditions: The UPF is not available to support the edge computingapplication.

Local DN Deployment

Introduction: An operator decides to deploy the local DN (e.g., 280_(i)) to connect to the UPF (e.g., 230 _(i)) that has been instantiatedto support edge computing. The local DN should be deployed in locationswhere the data transported between UPF and local DN should meet the QoStargets (e.g., or requirements, etc.) over N6 interface.

Pre-conditions: 3GPP management system has received the QoS targets(e.g., or requirements, etc.) over N6 interface. The UPF supporting theedge computing application (e.g., 270), has been instantiated.

Description: (1) 3GPP management system (e.g., 420) requests the edgecomputing management system (e.g., 434) to deploy the local DN (e.g.,280 _(i)) with the QoS targets (e.g., or requirements, etc.) over N6interface, and UPF information (e.g., the identifier of the UPF beinginstantiated, the location of the data center where the UPF is hosted);(2) Edge computing management system selects the data center (e.g., 290_(i)) where the local DN will be instantiated, based on the QoS targets(e.g., or requirements) and UPF location, and interacts with NFVO (e.g.,of NFV MANO 432) to instantiate the local DN in such data center; (3)Edge computing management system responds to 3GPP management system withthe identifier of the local DN being instantiated, after NFVO indicatingthat the local DN has been instantiated successfully; and (4) 3GPPmanagement system requests NFVO to connect the UPF to local DN with theQoS targets (e.g., or requirements) over N6 interface.

Post-conditions: UEs are able to communicate with the local DN to runthe edge computing application.

E2E OSS Deployment Scenario

Introduction: This use case is to support the E2E OSS (e.g., 410)deployment scenario. An operator decides to deploy the local DN (e.g.,280 _(i)) and UPF (e.g., 230 _(i)) to support edge computingapplications (e.g., 270) for UEs located in a specific area. E2E OSSderives the 5G QoS and QoS over N6 interface requirements from e2e QoSrequirements.

Pre-conditions: The NR cells (e.g., 310 _(i)) where UEs are connected torun the edge computing applications (e.g., 270) have been deployed.

Description: (1) E2E OSS requests 3GPP management system to deploy theUPF with 5G QoS targets (e.g., or requirements) in a specific area; (2)3GPP management system (e.g., 420) selects the data center (e.g., 290_(i)) where the UPF will be instantiated, based on the 5G QoS targets(e.g., or requirements), and interacts with NFVO (e.g., of NFV MANO 432)to instantiate the UPF in such data center; (3) 3GPP management systemresponds to E2E OSS with the identifier and the location of the UPFbeing instantiated, after NFVO indicating that the UPF has beeninstantiated successfully; (4) E2E OSS requests non-3GPP edge computingmanagement system (e.g., 434) to deploy the local DN with the QoS overN6 requirements, and the UPF location; (5) Non-3GPP edge computingmanagement system selects the data center where the local DN will beinstantiated, based on the QoS over N6 targets (e.g., or requirements)and UPF location, and interacts with NFVO to instantiate the local DN insuch data center; (6) Non-3GPP edge computing management system respondsto E2E OSS with the identifier of the local DN being instantiated, afterNFVO responds that the AS has been instantiated successfully; and (7)E2E OSS requests NFVO to connect UPF to local DN with the non-3GPPnetworks QoS requirements.

Post-conditions: UEs are able to communicate with the local DN to runthe edge computing application.

RAN Condition Data

Introduction: Self-driving cars communicate with applications hosted inthe edge computing based on ultra-low latency and high reliabilityconnections as they travel to the destinations. Any service interruptionin NR cells (e.g., 310 _(i)) along the way where the cars are travelingcan cause issues, including property damage or even bodily injury. 3GPPmanagement system (e.g., 420) analyzes performance data, alarms, andprovisioning data of NR cells to generate RAN condition data indicatingthe issues of a NR cell before the cars reach that NR cell. 3GPPmanagement system then reports to edge computing management system(e.g., 434) the RAN condition data that can be consumed by edgecomputing application to re-route cars when it foresees certain cellsare experiencing issues. For example, if a cell is overloaded with usertraffic, experiencing an outage, or not able to support the ultra-lowlatency requirement, then this cell should not be in the route.

Pre-conditions: An edge computing application is running to supportautonomous driving.

Description: (1) 3GPP management system collects and analyzesperformance data, alarms, and provisioning data of NR cells; (2) 3GPPmanagement system generates RAN condition data that comprises but is notlimited to the following value to represent the condition of a NR cell(0: healthy; 1: out of service; 2: capacity constraint (e.g.overloaded); 3: capability constraint (e.g. does not support ultra-lowlatency requirement)); and (3) 3GPP management system provides the RANcondition data to edge computing management system to support autonomousdriving.

Post-conditions: Edge computing application uses the RAN condition datato assist the auto navigation.

Potential Capabilities or Requirements

In various embodiments, one or more of the following capabilities orrequirements can be employed by a 3GPP management system.

REQ-ECM_CON-w: The 3GPP management system can have a capability toinstantiate the UPF at the location that meets the 5G QoS requirements.

REQ-ECM_CON-x: The 3GPP management system can have a capability toconfigure the SMF to add an UPF to the UPF list with the UPF location toassist UPF selection for traffic steering.

REQ-ECM_CON-y: The 3GPP management system can have a capability toterminate the UPF that has been supporting the edge computing.

REQ-ECM_CON-z: The 3GPP management system can have a capability toconfigure the SMF to remove the UPF to the UPF list serving the edgecomputing.

REQ-ECM_CON-x: The 3GPP management system can have a capability forrequesting edge computing management system to deploy local DN based onQoS requirements over N6 interface, and the UPF location.

REQ-ECM_CON-y: The 3GPP management system can have a capability forrequesting NFVO to connect UPF to the local DN based on QoS requirementsover N6 interface.

REQ-ECM_CON-x: The 3GPP management system can have a capability allowingE2E OSS to deploy UPF based on 5G QoS.

REQ-ECM_CON-x: 3GPP management system can have a capability to provideRAN condition data to edge computing management system to supportautonomous driving.

Additional Embodiments

Examples herein can include subject matter such as a method, means forperforming acts or blocks of the method, at least one machine-readablemedium including executable instructions that, when performed by amachine (e.g., a processor with memory, an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA), orthe like) cause the machine to perform acts of the method or of anapparatus or system for concurrent communication using multiplecommunication technologies according to embodiments and examplesdescribed.

A first example embodiment is an E2E OSS (Operations Support System)comprising one or more processors configured to: request a 3GPPmanagement system to deploy the UPF with the 5G QoS targets (e.g., orrequirements) in a specific location; receive the response from 3GPPmanagement system with the identifier and the location of the UPF beinginstantiated; request non-3GPP edge computing management system todeploy the Local DN with the QoS targets (e.g., or requirements) over N6interface, and the UPF location; receive the response from non-3GPP edgecomputing management system with the identifier of the local DN beinginstantiated; and request NFVO to connect UPF to local DN with the QoStargets (e.g., or requirements) over N6 interface.

A second example embodiment comprises the first example embodiment,wherein the 3GPP management system comprises one or more processorsconfigured to: select the data center where the UPF will beinstantiated, based on the 5G QoS targets (e.g., or requirements) andthe location of NR cells; and request NFVO to instantiate the UPF insuch data center identified in the above step; and receive a responsefrom NFVO with the identifier of UPF to indicate the UPF has beeninstantiated.

A third example embodiment comprises the second example embodiment,wherein upon receiving a response from NFVO, the 3GPP management systemis configured to respond to E2E OSS with the identifier and the locationof the UPF being instantiated, after the UPF has been instantiatedsuccessfully.

A fourth example embodiment comprises the first example embodiment,wherein the non-3GPP edge computing management system comprises one ormore processors configured to: receive a request from 3GPP managementsystem to deploy the local DN with the QoS targets (e.g., orrequirements) over N6 interface, and UPF information (e.g. theidentifier of the UPF being instantiated, the location of the datacenter where the UPF is hosted); select the data center where the localDN will be instantiated, based on the QoS targets (e.g., orrequirements) and the location of UPF; request NFVO to instantiate thelocal DN in such data center identified in the above step; and receive aresponse from NFVO with the identifier of local DN to indicate the UPFhas been instantiated.

A fifth example embodiment comprises the fourth example embodiment,wherein upon receiving a response from NFVO, the non-3GPP edge computingmanagement system is configured to respond to 3GPP management systemwith the identifier of the local DN being instantiated.

A sixth example embodiment comprises any of the first through fifthexample embodiments, wherein the edge computing applications are hostedin the local DN that is closer to the UE's access point of attachment orRAN in order to reduce the end-to-end latency and the load on thetransport network by the edge computing application.

A seventh example embodiment is a 3GPP management system comprising oneor more processors configured to: receive a request with the 5G QoStargets (e.g., or requirements) to deploy the UPF in a specificlocation; select the data center where the UPF will be instantiated,based on the 5G QoS targets (e.g., or requirements); request NFVO toinstantiate the UPF in such data center identified in the above step;receive a response from NFVO with the identifier of UPF to indicate theUPF has been instantiated; and configure SMF to add the newlyinstantiated UPF to the UPF list with the UPF location to assist UPFselection for traffic steering.

An eighth example embodiment is a 3GPP management system comprising oneor more processors configured to: receive a request with to terminatethe UPF; request NFVO to terminated the UPF; receive a response fromNFVO with the identifier of UPF to indicate the UPF has been terminated;and configure SMF to remove the UPF that has been terminated from UPFlist serving the edge computing.

A ninth example embodiment is a 3GPP management system comprising one ormore processors configured to: collect and analyzes performance data,alarms, and provisioning data of NR cells; generate RAN condition datathat include but not limited to the following value to represent thecondition of a NR cell (0: healthy; 1: out of service 2: capacityconstraint (e.g. overloaded); 3: capability constraint (e.g. does notsupport ultra-low latency requirement)); provide the RAN condition datato edge computing management system to support autonomous driving.

The following are additional example embodiments.

Example 1 is an apparatus configured to be employed in a 3GPP (ThirdGeneration Partnership Project) management system, comprising: a memoryinterface; and processing circuitry configured to: generate a firstrequest for a NFVO (NFV (Network Function Virtualization) Orchestrator)to instantiate a UPF (User Plane Function) at a location that isdetermined by 5G (Fifth Generation) QoS (Quality of Service)requirements; process a first response from the NFVO indicating that theUPF has been instantiated successfully; and configure a SMF (SessionManagement Function) to add the UPF to a UPF list with a location of theUPF.

Example 2 comprises the subject matter of any variation of any ofexample(s) 1, wherein the UPF list facilitates UPF selection for trafficsteering.

Example 3 comprises the subject matter of any variation of any ofexample(s) 1-2, wherein the processing circuitry is further configuredto process the 5G QoS requirements, wherein the 5G QoS requirements areassociated with the connection between a UE (User Equipment) and theUPF.

Example 4 comprises the subject matter of any variation of any ofexample(s) 3, wherein the 5G QoS requirements are derived fromend-to-end QoS requirements from the UE to an edge computingapplication, and received via an additional request that is associatedwith the edge computing application.

Example 5 comprises the subject matter of any variation of any ofexample(s) 4, wherein the additional request indicates the location.

Example 6 comprises the subject matter of any variation of any ofexample(s) 1-5, wherein the processing circuitry is further configuredto: generate a second request for the NFVO to terminate the UPF; processa second response from the NFVO indicating that the UPF has beenterminated successfully; and configure the SMF to remove the UPF fromthe UPF list.

Example 7 is an apparatus configured to be employed in a 3GPP (ThirdGeneration Partnership Project) management system, comprising: a memoryinterface; and processing circuitry configured to: generate a firstrequest for an edge computing management system to deploy a local DN(Data Network), wherein the first request comprises QoS (Quality ofService) requirements and information associated with a UPF (User PlaneFunction); process a response from the edge computing management system,wherein the response comprises an identifier of the local DN; andgenerate a second request for a NFVO (Network Function VirtualizationOrchestrator) to connect the UPF to the local DN over an N6 interfacebased on the QoS requirements.

Example 8 comprises the subject matter of any variation of any ofexample(s) 7, wherein the information associated with the UPF comprisesat least one of an identifier of the UPF or a location of a data centerwhere the UPF is hosted.

Example 9 comprises the subject matter of any variation of any ofexample(s) 7-8, wherein the UPF was instantiated to support one or moreedge computing applications.

Example 10 comprises the subject matter of any variation of any ofexample(s) 7-9, wherein the QoS requirements comprise QoS requirementsfor the N6 interface.

Example 11 is an apparatus configured to be employed in an edgecomputing management system, comprising: a memory interface; andprocessing circuitry configured to: process a request from a 3GPP (ThirdGeneration Partnership Project) management system to deploy a local DN(Data Network), wherein the request comprises QoS (Quality of Service)requirements and information associated with a UPF (User PlaneFunction); select a data center where the local DN will be instantiated,based on the QoS requirements and the information associated with theUPF; interact with a NFVO (Network Function Virtualization Orchestrator)to instantiate the local DN in the selected data center; receive anindication from the NFVO that the local DN has been instantiatedsuccessfully; and generate a response for the 3GPP management system,wherein the response comprises an identifier of the local DN.

Example 12 comprises the subject matter of any variation of any ofexample(s) 11, wherein the information associated with the UPF comprisesat least one of an identifier of the UPF or a location of a data centerwhere the UPF is hosted.

Example 13 comprises the subject matter of any variation of any ofexample(s) 11-12, wherein the UPF was instantiated to support one ormore edge computing applications.

Example 14 comprises the subject matter of any variation of any ofexample(s) 11-13, wherein the QoS requirements comprise QoS requirementsfor the N6 interface.

Example 15 is an apparatus configured to be employed in a 3GPP (ThirdGeneration Partnership Project) management system, comprising: a memoryinterface; and processing circuitry configured to: collect dataassociated with one or more NR (New Radio) cells of a RAN (Radio AccessNetwork); analyze the collected data; generate RAN condition data basedon the analyzed data; and provide the RAN condition data to an edgecomputing management system.

Example 16 comprises the subject matter of any variation of any ofexample(s) 15, wherein the data associated with a set of NR cells of aRAN comprises one or more of performance data, alarm data, orprovisioning data.

Example 17 comprises the subject matter of any variation of any ofexample(s) 15, wherein the RAN condition data comprises, for a first NRcell of the set of NR cells, an associated value that represents acondition of the first NR cell.

Example 18 comprises the subject matter of any variation of any ofexample(s) 17, wherein the associated value indicates whether thecondition of the first NR cell is one of: healthy, out of service,capacity constrained, or capability constrained.

Example 19 comprises the subject matter of any variation of any ofexample(s) 15-18, wherein the processing circuitry is configured toanalyze the collected data based on requirements associated with an edgecomputing application.

Example 20 comprises the subject matter of any variation of any ofexample(s) 19, wherein the edge computing application comprisesauto-navigation associated with autonomous driving.

Example 21 is an apparatus configured to be employed in a NFVO (NetworkFunction Virtualization Orchestrator), comprising: a memory interface;and processing circuitry configured to: process a request from a 3GPP(Third Generation Partnership Project) management system to instantiatea UPF (User Plane Function) at a location that is determined by 5G(Fifth Generation) QoS (Quality of Service) requirements; instantiatethe UPF at the location in response to the request; and generate aresponse for the 3GPP management system indicating that the UPF has beeninstantiated successfully.

Example 22 comprises the subject matter of any variation of any ofexample(s) 21, wherein the 5G QoS requirements are associated with anedge computing application.

Example 23 is an apparatus configured to be employed in an E2E(End-to-End) OSS (Operations Support System), comprising: a memoryinterface; and processing circuitry configured to: generate a firstrequest for a 3GPP (Third Generation Partnership Project) managementsystem to deploy a UPF (User Plane Function) based on 5G (FifthGeneration) QoS (Quality of Service) requirements in an area; process afirst response from the 3GPP management system, wherein the firstresponse comprises an identifier of the UPF and a location of the UPF;generate a second request for a non-3GPP edge computing managementsystem to deploy a local DN (Data Network) based on QoS requirements foran N6 interface, wherein the second request indicates the location ofthe UPF; process a second response from the non-3GPP edge computingmanagement system, wherein the second response comprises an identifierof the local DN; and generate a third request for a NFVO (NetworkFunction Virtualization Orchestrator) to connect the UPF to the local DNbased on the QoS requirements for the N6 interface.

Example 24 is an apparatus configured to be employed in a 3GPP (ThirdGeneration Partnership Project) management system, comprising: a memoryinterface; and processing circuitry configured to: generate a requestfor a NFVO (NFV (Network Function Virtualization) Orchestrator) toterminate a UPF (User Plane Function); process a response from the NFVOindicating that the UPF has been terminated successfully; and configurea SMF (Session Management Function) to remove the UPF from a UPF list.

Example 25 comprises the subject matter of any variation of any ofexample(s) 24, wherein the UPF list facilitates UPF selection fortraffic steering for one or more edge computing applications.

Example 26 comprises the subject matter of any variation of any ofexample(s) 24, wherein the response comprises an identifier of the UPF.

Example 27 comprises an apparatus comprising means for executing any ofthe described operations of examples 1-26.

Example 28 comprises a machine readable medium that stores instructionsfor execution by a processor to perform any of the described operationsof examples 1-26.

Example 29 comprises an apparatus comprising: a memory interface; andprocessing circuitry configured to: perform any of the describedoperations of examples 1-26.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In particular regard to the various functions performed by the abovedescribed components or structures (assemblies, devices, circuits,systems, etc.), the terms (including a reference to a “means”) used todescribe such components are intended to correspond, unless otherwiseindicated, to any component or structure which performs the specifiedfunction of the described component (e.g., that is functionallyequivalent), even though not structurally equivalent to the disclosedstructure which performs the function in the herein illustratedexemplary implementations. In addition, while a particular feature mayhave been disclosed with respect to only one of several implementations,such feature can be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application.

1.-20. (canceled)
 21. An apparatus configured to be employed in a 3GPP(Third Generation Partnership Project) management system, comprising: amemory interface; and processing circuitry configured to: generate afirst request for an edge computing management system to deploy a localDN (Data Network), wherein the first request comprises QoS (Quality ofService) requirements and information associated with a UPF (User PlaneFunction); process a response from the edge computing management system,wherein the response comprises an identifier of the local DN; andgenerate a second request for a NFVO (Network Function VirtualizationOrchestrator) to connect the UPF to the local DN over an N6 interfacebased on the QoS requirements.
 22. The apparatus of claim 21, whereinthe information associated with the UPF comprises at least one of anidentifier of the UPF or a location of a data center where the UPF ishosted.
 23. The apparatus of claim 21, wherein the UPF was instantiatedto support one or more edge computing applications.
 24. The apparatus ofclaim 21, wherein the QoS requirements comprise QoS requirements for theN6 interface.
 25. An apparatus configured to be employed in an edgecomputing management system, comprising: a memory interface; andprocessing circuitry configured to: process a request from a 3GPP (ThirdGeneration Partnership Project) management system to deploy a local DN(Data Network), wherein the request comprises QoS (Quality of Service)requirements and information associated with a UPF (User PlaneFunction); select a data center where the local DN will be instantiated,based on the QoS requirements and the information associated with theUPF; interact with a NFVO (Network Function Virtualization Orchestrator)to instantiate the local DN in the selected data center; receive anindication from the NFVO that the local DN has been instantiatedsuccessfully; and generate a response for the 3GPP management system,wherein the response comprises an identifier of the local DN.
 26. Theapparatus of claim 25, wherein the information associated with the UPFcomprises at least one of an identifier of the UPF or a location of adata center where the UPF is hosted.
 27. The apparatus of claim 25,wherein the UPF was instantiated to support one or more edge computingapplications.
 28. The apparatus of claim 25, wherein the QoSrequirements comprise QoS requirements for the N6 interface.
 29. Anapparatus configured to be employed in a 3GPP (Third GenerationPartnership Project) management system, comprising: a memory interface;and processing circuitry configured to: collect data associated with oneor more NR (New Radio) cells of a RAN (Radio Access Network); analyzethe collected data; generate RAN condition data based on the analyzeddata; and provide the RAN condition data to an edge computing managementsystem.
 30. The apparatus of claim 29, wherein the data associated witha set of NR cells of a RAN comprises one or more of performance data,alarm data, or provisioning data.
 31. The apparatus of claim 29, whereinthe RAN condition data comprises, for a first NR cell of the set of NRcells, an associated value that represents a condition of the first NRcell.
 32. The apparatus of claim 31, wherein the associated valueindicates whether the condition of the first NR cell is one of: healthy,out of service, capacity constrained, or capability constrained.
 33. Theapparatus of claim 29, wherein the processing circuitry is configured toanalyze the collected data based on requirements associated with an edgecomputing application.
 34. The apparatus of claim 33, wherein the edgecomputing application comprises auto-navigation associated withautonomous driving.